feat: add ft api-keys create|list|revoke - #30
Merged
Conversation
Self-service management of service API keys against the /api/v1 endpoints added in backend #285 (contract v1.5.0): - create <name> [--scope read|write] [--expires <iso>]: mints a key and prints the plaintext secret exactly once with a warning. - list: paginated table (never returns the secret), --all/--csv/--columns. - revoke <id>: DELETE with confirmation unless --yes. Regenerated the SDK from the updated openapi.json (v1.5.0). Includes a changeset (minor) and a structural command test. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Comando de CLI para gestionar API keys de servicio self-service, mitad cliente del backend #285 (contrato
/api/v1v1.5.0).Subcomandos
ft api-keys create <name> [--scope read|write] [--expires <iso>]— mintea una key e imprime el secreto en claro una sola vez con advertencia (o--jsonpara el objeto completo). Default--scope read.ft api-keys list [--all --csv --columns --limit --cursor]— tabla paginada (name,keyPrefix,scope,lastUsedAt,expiresAt,revokedAt); nunca devuelve el secreto.ft api-keys revoke <id> [--yes]— DELETE con confirmación.Todos comparten
--workspacecomo el resto del CLI.Detalle
pnpm generate) desdeopenapi.jsonv1.5.0. Funciones consumidas:postApiKeys,getApiKeys,deleteApiKeysId.registerResource) por la UX especial decreate(secreto mostrado una vez) yrevoke.pnpm typecheck/pnpm lint/pnpm testen verde.🤖 Generated with Claude Code